Microsoft has removed a fabulous document explaining the "necessary limitations" of Windows 10 on Arm chips.

The document, 'Limitations of apps and experiences on Arm' appeared on Friday on Microsoft's Windows Dev Center, quickly gaining coverage because Microsoft hadn't yet explained how Windows 10 on Arm would definitely be different to Windows 10 on x86, and just what type of performance impact emulation would probably have on apps.

Microsoft has now killed the page 'Limitations of apps and experiences on Arm', while the URL redirects to the more neutral Troubleshooting x86 Desktop Apps page.

The latest page carries across examples of content described in the last document but using less awareness of limitations, in particular Hyper-V not being supported on Windows on Arm. Microsoft also removed the table shown below, describing app architecture types supported on Arm.

The previous document explained that 64-bit apps are not likely to work on Windows 10 on Arm. Only 32-bit x86 desktop apps work.

Games and apps who use a type of OpenGL later than version 1.1, or require hardware-accelerated OpenGL, are broken. However, Arm does support x86 apps who use DirectX 9, DirectX 10, DirectX 11, and DirectX 12.

Some types of apps that get a new Windows experience wouldn't work correctly because native OS components cannot load non-native components, it said.

This limitation includes input method editors (IMEs) and assistive technologies. Also, cloud storage apps may well not work when they often use shell extensions, similar to icons in Explorer, which will fail.

You'll find it noted that only Arm64 drivers are supported, so while Windows 10 on Arm can emulate x86 applications, this doesn't happen support drivers for other architectures including x64 or x86.

Fifth, it said Microsoft's Hyper-V isn't supported, meaning no VMs using Microsoft's hypervisor technology.

A table listing issues and solutions will be moved to the troubleshooting x86 desktop apps page, there are still references towards the issues, but with no emphasis on "limitations" of Windows 10 on Arm previously described across six bullet points.

As for apps that customize the Windows experience, Microsoft has posted the right section explaining shell extensions on Arm.

"Apps that you'll want to hook Windows components or load their DLLs into Windows processes might want to recompile those DLLs correspond the architecture of your system; ie Arm64. Typically, this is used by input method editors (IMEs), assistive technologies, and shell extension apps (eg to celebrate cloud storage icons in Explorer maybe a right-click Context menu)."

Microsoft also notes that Arm64 Win32 SDK support is on its way soon.

In addition has an updated section on x86 apps that rely on drivers, which require to be recompiled for Arm.

"All kernel-mode drivers, User-Mode Driver Framework (UMDF) drivers, and print drivers is required to be compiled to accommodate the architecture of these OS. Vehicle x86 app will have a driver, then that driver is required to be recompiled for Arm64.

"The x86 app may run fine under emulation. However, its driver will have to be recompiled for Arm64 and then any app experience that relies on the driver probably will not be available. Take a look at about compiling your driver for Arm64, see Building ARM64 Drivers of your WDK."